Verify each finding against the current code and only fix it if needed.

Inline comments:
In @.claude/agents/code-quality-fixer.md:
- Around line 28-30: Specify clear retry semantics for the orchestration
contract: document input parameters for retry (batch range or specific batch
IDs), and define the merge strategy for result keys
`_workspace/01_analyzer_issues.json` fields `fixed`, `failed`, `skipped`, and
`changed_files` (options: accumulate/union, overwrite, or last-run-only),
include idempotency guarantees (how duplicate runs are detected and ignored),
and add an explicit "reset" flag or versioning to force overwrite when desired;
update the contract text around `_workspace/01_analyzer_issues.json` to state
these rules and reference the keys `fixed`, `failed`, `skipped`, `changed_files`
so QA can deterministically merge or replace results on retries.

In @.claude/agents/pr-creator.md:
- Around line 76-82: 출력 스키마에 실패 케이스가 빠져 있어서 오케스트레이터가 성공/실패를 구분할 수 없으니, 현재 JSON
예시(예: the object containing "pr_url","branch","commit_sha") 옆에 실패 응답 스키마를 추가해
주세요; 구체적으로 출력 스키마에 success:boolean, error:string (열거값: "QA_NOT_APPROVED" |
"GIT_PUSH_FAILED" | "PR_CREATE_FAILED"), message:string(구체적 에러 메시지),
details:object(추가 정보)을 포함시키고 에러 발생 시 해당 구조를 반환하도록 문서/예시를 갱신하세요.
- Line 20: 명확하지 않은 "작업 원칙 6"의 동작을 다음처럼 규정하세요: 동일 브랜치에 기존 PR이 있으면 새로운 PR은 생성하지 않고
기존 PR의 URL을 반환하되, 에이전트는 필요시 브랜치에 커밋은 푸시(pushCommits)하되 PR의 제목/본문은 수정하지
않습니다(unless updatePR flag is true). 즉, createPR는 호출하지 않고 existingPR을 반환하고,
updatePR은 명시적 플래그가 있을 때만 실행되도록 PR 생성/업데이트 흐름(createPR, updatePR, pushCommits)을
문서에 명시해 주세요.
- Line 72: 문서의 "PR 타입: `quality-fix` 또는 `feature`" 항목이 어디서 오는지 명시되어 있지 않으니,
.claude/agents/pr-creator.md의 해당 항목을 수정해 PR 타입 입력의 출처와 전달방식을 명확히 기재하세요; 예를 들어
"PR 타입(prType)은 오케스트레이터 스킬 koin-pipeline에서 agent 호출 시 입력 파라미터로 전달된다"라고 명시하고, 입력
파라미터 이름(prType), 허용값(`quality-fix`, `feature`), 그리고 수신 코드(예: generatePR 함수 또는
PRCreator agent의 입력 스키마)에서 이를 검증하는 방식(기본값/검증 에러 처리)을 간단히 기술하도록 변경하세요.

In @.claude/agents/qa-reviewer.md:
- Line 76: 출력 스키마(현재 54-70줄)에 누락된 `notes` 필드를 추가하세요: 스키마에 "notes" : { "type":
"string", "description": "파일 건너뜀 등 추가 정보(선택적)" } 형태로 정의하고 기본값/옵셔널로 처리하며, 스키마를
사용하는 검증/직렬화 로직(예: QA 응답 생성/예시 JSON)과 예제 출력(제시된 "파일 src/missing.ts를 찾을 수 없어 건너뜀"
문구)을 함께 갱신해 `notes`가 실제로 포함될 수 있도록 하세요.
- Line 16: Clarify the "점진적 검증" principle in the sentence "검증은 전체 완성 후 한 번이 아니라,
수정된 파일 단위로 점진적으로 수행한다" by specifying scope and process: change it to state that
validations run per change-set/commit (not literally per single file), describe
dependency-aware behavior (e.g., when API types or hooks change, run
dependent-unit and integration tests), and define "점진적" as validating
independent changes first and then running broader integration checks for
dependent files; alternatively provide an explicit removal instruction if you
prefer to drop the principle.

In @.claude/agents/sonarcloud-analyzer.md:
- Around line 18-19: Update the batch constraints in the sonarcloud-analyzer.md
guidance so it matches the sonarcloud-analysis skill contract: locate the list
item that reads "파일당 이슈 수가 많은 경우, 한 번에 처리할 수 있는 범위(파일 10개 이내)로 배치를 나눈다." and add
the missing constraint "배치당 최대 이슈 50개 (sonarcloud-analysis 제약)" so both the
analyzer and fixers use the same batching rule; ensure the phrase
'sonarcloud-analysis' and '배치당 최대 이슈 50개' appear together in that section to
make the contract explicit.

In @.claude/CLAUDE.md:
- Around line 71-74: 현재 문서의 "**변경 이력:**" 섹션에 있는 Markdown 표(| 날짜 | 변경 내용 | 대상 |
사유 | ...)가 앞뒤에 빈 줄이 없어 markdownlint MD058 경고가 발생합니다; 해당 표를 찾을 때는 "**변경 이력:**" 헤더
또는 표 시작 행("| 날짜 | 변경 내용 | 대상 | 사유 |")를 기준으로 표 바로 위에 한 줄, 표 바로 아래에 한 줄의 빈 줄을 추가해
주세요.

In @.claude/skills/github-pr-creation/SKILL.md:
- Around line 37-43: Add a language identifier to the fenced code block that
contains the commit message examples (the block starting with "feat: [기능명] 추가"
and including "fix:", "refactor:", "style:", "chore:") to satisfy markdownlint
MD040; edit the fence to start with ```text (or ```bash) so the code block
language is explicitly specified.

In @.claude/skills/koin-pipeline/SKILL.md:
- Line 191: The documentation currently instructs setting SONAR_HOST_URL
alongside SONAR_TOKEN but other docs state SONAR_HOST_URL is unnecessary for
SonarCloud; update SKILL.md to match that standard by removing the
SONAR_HOST_URL requirement or clarifying that only SONAR_TOKEN is needed for
SonarCloud usage. Find the section that mentions SONAR_HOST_URL and SONAR_TOKEN
and either delete the SONAR_HOST_URL entry or change its wording to indicate it
is only required for self-hosted SonarQube (keep SONAR_TOKEN as the required env
var), and ensure the wording matches other project docs for consistency.
- Line 20: The doc currently shows the move command "mv _workspace/
_workspace_prev/" which can fail or overwrite when _workspace_prev exists;
update the instructions to handle that case by choosing a safe rename policy
(e.g., append a timestamp or incrementing suffix) or explicitly remove/archive
the existing folder first; revise the SKILL.md text at the line containing "mv
_workspace/ _workspace_prev/" to describe the chosen behavior (timestamped
archive like _workspace_prev_YYYYMMDD_HHMMSS or a deterministic cleanup step)
and state the failure/overwrite semantics so users know whether the command will
fail, overwrite, or create a new timestamped directory.
- Line 82: Update the retry loop in the SKILL pipeline step(s) labeled
"approved: false" and the A-2 re-run path to explicitly track and increment a
retry counter (e.g., retry_count) in the step contract, stop retrying after 2
attempts, and include the list of P0 issues in the payload passed into the A-2
re-execution (so the re-run receives the P0 issue list); ensure this contract
change is applied to every occurrence referenced (the loop/step definitions
around the existing "approved: false" entries and the A-2 re-run logic mentioned
at lines 82, 151 and 174) so infinite or invalid retries are prevented and the
A-2 run receives P0 data.

In @.claude/skills/qa-review/SKILL.md:
- Around line 53-56: The check title "절대 경로 임포트 확인" and the grep pattern `grep
-n "from '\.\./" src/[changed-path]` are inconsistent; either update the title
to "상대 경로 임포트 확인" to match the `from '../` pattern, or change the grep pattern
to search for absolute imports (e.g., a pattern matching `from 'src/` or `from
'@/`) to match the "절대 경로 임포트 확인" intent; update the string literal in the
SKILL.md snippet so the title and the grep pattern refer to the same import
style.
- Around line 25-29: Replace the problematic invocation "yarn dlx tsc --noEmit"
(shown in the SKILL.md snippet) with a fixed-dependencies invocation: either use
"yarn exec tsc --noEmit" or "npx tsc --noEmit", or add a "tsc": "tsc" script to
package.json and run that (e.g., "yarn tsc --noEmit"); update the SKILL.md
example to show the chosen command so CI/local typechecks use the repo's locked
TypeScript version instead of dlx.

In @.claude/skills/sonarcloud-analysis/references/sonarcloud-setup.md:
- Line 64: Replace the non-deterministic reference
SonarSource/sonarcloud-github-action@master with a pinned commit SHA (e.g.,
SonarSource/sonarcloud-github-action@<commit-sha>) to ensure immutable workflow
execution; locate the `uses: SonarSource/sonarcloud-github-action@master` entry
and swap the tag for a specific commit SHA, and consider updating the workflow
to use the newer `SonarSource/sonarqube-scan-action` in the long term since the
current action is deprecated.

In @.claude/skills/sonarcloud-analysis/SKILL.md:
- Around line 15-16: 예시값 SONAR_PROJECT_KEY의 불일치 문제: 현재 샘플 값 "koin_web_recode"를
프로젝트에서 통용되는 키 규칙으로 통일된 값인 "BCSDLab_KOIN_WEB_RECODE"로 변경하고, SONAR_PROJECT_KEY를
참조하는 다른 문서(예: setup 문서, sonar-project.properties)와 동일하게 맞춰 동기화하세요; 해당 키를 사용하는 모든
설정/스크립트에서 변수 이름(SONAR_PROJECT_KEY)과 값이 일치하는지 확인해 수정하면 API 조회 실패를 방지할 수 있습니다.

---

Nitpick comments:
In @.claude/agents/qa-reviewer.md:
- Line 44: The checklist item "주요 사용자 인터랙션에 `useLogger()` 존재" is too vague;
update the entry in qa-reviewer.md to enumerate concrete interaction types so QA
can auto-verify: replace the single checkbox with specific sub-items such as "버튼
클릭 이벤트 핸들러에 `useLogger()` 적용", "폼 제출 핸들러에 `useLogger()` 적용", "모달/다이얼로그 열기·닫기에서
`useLogger()` 사용", and "탭/페이지 전환 시 `useLogger()` 적용" and keep the original
`useLogger()` wording so reviewers can match the symbol exactly.
- Around line 54-70: Add a TypeScript-style interface comment to the
`_workspace/03_qa_result.json` output schema that documents each field's type
and optionality (e.g., lint_passed: boolean, approved: boolean, summary: string,
issues: Array<Issue> where Issue has severity: string, file: string, line?:
number, message: string, suggestion?: string), explicitly note that `issues` can
be an empty array, and clarify which fields like `line` and `suggestion` are
optional vs required so consumers of the QA output (e.g., readers of
`_workspace/03_qa_result.json`) have an unambiguous contract.

In @.claude/skills/sonarcloud-analysis/SKILL.md:
- Around line 26-29: The documentation claims "페이지네이션 포함" but the example only
shows a single curl call; update SKILL.md to show how to paginate using the curl
example by demonstrating the `p` (page) parameter (and `ps` page size) in a loop
or a total-based repeat; reference the existing curl command and explain
incrementing `p` (or checking `total`/`paging` in the JSON) until all issues are
retrieved so readers can run multiple requests to collect every page.

In @.github/workflows/sonarcloud.yml:
- Around line 23-24: In the GitHub Actions CI step named "Install package" (the
step that currently runs the `yarn` command) change the command to explicitly
include the immutable flag by replacing the plain `yarn` invocation with `yarn
--immutable` so the lockfile integrity is enforced in CI; ensure the step that
runs `yarn` uses the `--immutable` flag to make the intent explicit and
guarantee reproducible installs.